Skip to content

Show 'Verify this device' toast even if there are no encrypted rooms yet#32891

Merged
andybalaam merged 2 commits intodevelopfrom
andybalaam/always-nag-to-verify-even-if-no-e2e-rooms
Apr 24, 2026
Merged

Show 'Verify this device' toast even if there are no encrypted rooms yet#32891
andybalaam merged 2 commits intodevelopfrom
andybalaam/always-nag-to-verify-even-if-no-e2e-rooms

Conversation

@andybalaam
Copy link
Copy Markdown
Member

@andybalaam andybalaam commented Mar 23, 2026

Part of https://github.com/element-hq/crypto-internal/issues/305

Depends on #32931

Checklist

@andybalaam andybalaam changed the title Andybalaam/always nag to verify even if no e2e rooms Show 'Verify this device' toast even if there are no encrypted rooms yet Mar 23, 2026
@andybalaam andybalaam force-pushed the andybalaam/always-nag-to-verify-even-if-no-e2e-rooms branch from ff49ee0 to 9890505 Compare March 25, 2026 11:13
@andybalaam andybalaam force-pushed the andybalaam/always-nag-to-verify-even-if-no-e2e-rooms branch from a463e30 to 4597d73 Compare March 25, 2026 11:43
@andybalaam andybalaam force-pushed the andybalaam/always-nag-to-verify-even-if-no-e2e-rooms branch from 3861127 to 6fe9ff7 Compare March 25, 2026 15:37
@andybalaam andybalaam force-pushed the andybalaam/always-nag-to-verify-even-if-no-e2e-rooms branch from 6fe9ff7 to 8e4be76 Compare March 30, 2026 12:04
@andybalaam andybalaam force-pushed the andybalaam/always-nag-to-verify-even-if-no-e2e-rooms branch from ff77e2a to d87e682 Compare March 31, 2026 11:14
@andybalaam andybalaam force-pushed the andybalaam/always-nag-to-verify-even-if-no-e2e-rooms branch from d87e682 to 7adfd7d Compare March 31, 2026 11:32
@andybalaam andybalaam added this pull request to the merge queue Apr 9, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Apr 9, 2026
@andybalaam andybalaam added this pull request to the merge queue Apr 10, 2026
github-merge-queue Bot pushed a commit that referenced this pull request Apr 10, 2026
…yet (#32891)

* Show 'Verify this device' toast even if there are no encrypted rooms yet

* Add missing word

Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>

* Close Verify toast at the start of several more tests

* Reinstate comment about not showing toasts while secret storage is being accessed

* Close verify toast in room-list-sections test

* Share code to silence SonarQube

* Close verify toast in lowbandwidth.spec.ts

* Share code in Bob creation

* More attempts to silence SonarQube

---------

Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>
@t3chguy
Copy link
Copy Markdown
Member

t3chguy commented Apr 10, 2026

@andybalaam I suggest opening the HTML report to inspect the failure. It is not a flake. The element-modules tests are failing due to the toast being in their way.

@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Apr 10, 2026
@andybalaam
Copy link
Copy Markdown
Member Author

@andybalaam I suggest opening the HTML report to inspect the failure. It is not a flake. The element-modules tests are failing due to the toast being in their way.

Thanks, today I learned that clicking "View Deployment" next to "github-actions bot deployed to EndToEndTests" opens a Playwright report with useful info.

@t3chguy
Copy link
Copy Markdown
Member

t3chguy commented Apr 10, 2026

That would be the report for the pull_request run. Not the merge_group run which runs additional tests. That html report you have to download from the merge queue CI run.

@andybalaam
Copy link
Copy Markdown
Member Author

That would be the report for the pull_request run. Not the merge_group run which runs additional tests. That html report you have to download from the merge queue CI run.

Where do I find that? I can see the failure messages at https://github.com/element-hq/element-web/actions/runs/24236141622 but not an HTML report.

@andybalaam
Copy link
Copy Markdown
Member Author

Where do I find that? I can see the failure messages at element-hq/element-web/actions/runs/24236141622 but not an HTML report.

Ah, on that same link, under Artifacts, the artifact called "html-report"?

@t3chguy
Copy link
Copy Markdown
Member

t3chguy commented Apr 10, 2026

Yes that's right

@andybalaam
Copy link
Copy Markdown
Member Author

Attempting to fix downstream tests with element-hq/element-modules#252

@andybalaam
Copy link
Copy Markdown
Member Author

Working on element-hq/element-modules#258 to fix the latest merge queue rejection.

@andybalaam
Copy link
Copy Markdown
Member Author

Instead, #33158 should fix the failures we saw in the merge queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants